Controller interface with multiple day programming

ABSTRACT

A controller equipped with a user interface having multiple-day programming capabilities, including methods of programming such devices, are disclosed. The user interface may include one or more menus or screens that can be used to program a schedule for one or more selected days during the week. An illustrative method of programming the controller may include the steps of entering a scheduling routine, selecting multiple days for schedule modification, changing the schedule parameters for one or more periods during the selected days, and then exiting the scheduling routine.

This application is a continuation of U.S. patent application Ser. No.10/726,201, filed Dec. 2, 2003, entitled CONTROLLER INTERFACE WITHMULTIPLE DAY PROGRAMMING.

FIELD OF THE INVENTION

The present invention relates generally to the field of programmablecontrollers for homes and/or buildings are their related grounds. Morespecifically, the present invention relates to simplified interfaces forsuch controllers having multiple-day programming capabilities.

BACKGROUND OF THE INVENTION

Controllers are used on a wide variety of devices and systems forcontrolling various functions in homes and/or buildings and theirrelated grounds. Some controllers have schedule programming thatmodifies device parameters such, as set points as a function of dateand/or time. Some such device or system controllers that utilizeschedule programming for controlling various functions in homes and/orbuildings and their related grounds include, for example, HVACcontrollers, water heater controllers, water softener controllers,security system controllers, lawn sprinkler controllers, and lightingsystem controllers.

In a typical HVAC application, for example, such controllers can beemployed to monitor and, if necessary, control various environmentalconditions occurring within a home or office building. The controllermay include a microprocessor that interacts with other components in thesystem to regulate the temperature, humidity, venting, and/or airquality occurring at one or more locations. An internal sensor locatedwithin the controller and/or one or more remote sensors may be employedto sense when the temperature and/or humidity level reaches a certainthreshold level, causing the controller to send a signal to activate ordeactivate one or more components in the system.

The controller may be equipped with a user interface that allows theuser to monitor and adjust various parameters of the controller. Withmore modern designs, the user interface typically comprises a liquidcrystal display (LCD) or light emitting diode (LED) display inset withina controller housing that contains a microprocessor or the like, an I/Ointerface, and other components of the controller. The user interfacemay include a menu-driven interface that allows the user to scrollthrough one or more menus or screens to adjust the different settings onthe controller. In some cases, a program within the controller promptsthe user at each menu or screen to input various commands into theinterface to adjust the controller settings.

In certain designs, the user interface can be configured to permit theuser to program the controller to run on a certain schedule. Forexample, the controller can include a scheduling routine that allows theuser to adjust the heat and cool set points for one or more periodsduring a particular day in order to conserve energy. Once the parametersfor that day have been programmed, the user can then repeat the processto change the settings for the other remaining days. With some designs,the controller may include a feature that allows the user to program aseparate schedule for weekday and weekend use, or to copy settings for aparticular day and apply those settings towards other days of the week.

Interaction with the user interface can often prove difficult,discouraging many users from attempting to program the controller to runon a schedule. While some modem controllers allow the user to copysettings from one day to another, the number of steps typically requiredto program the controller are often deemed too complex or timeconsuming. In some cases, the user interface may not allow the user toselect multiple days outside of the normal weekday/weekend scheme.Accordingly, there is an ongoing need in the art to decrease the timeand complexity associated with programming a controller to run amultiple-day schedule.

SUMMARY OF THE INVENTION

The present invention pertains to simplified interfaces for controllershaving multiple-day programming capabilities. In one illustrativeembodiment, a method of programming a multiple-day schedule in acontroller equipped with a user interface can include the steps ofentering a scheduling routine, selecting multiple days for schedulemodification, changing the schedule parameters for one or more periodsduring the selected days, and then exiting the scheduling routine. Theuser may select or de-select days of the week to be modified at anypoint within the scheduling routine, including at certain pre-selectedtimes. In some embodiments, the controller can be programmed to run theschedule for any day or combination of days, as desired by the user.

The controller may include a user interface that can be used for bothdisplaying and modifying various parameters within the controller. Forexample, the user interface can include a touch screen, displaypanel/keypad, or any other suitable device adapted to transmit variouscommands to and from the controller. A number of mechanical and/or softbuttons (e.g. variable function, software configured) may be configuredto accept input commands from the user. In certain embodiments, the userinterface can include a menu-driven interface that allows the user tonavigate through one or more menus or screens to modify variousoperational settings within the controller. The menu-driven interfacemay include a number of icons (e.g. descriptive buttons) prompting theuser to input various commands with, for example, the touch screen orkeypad. Using the interface, the user can program the controller to runa particular schedule for one or more days without having to copy thesettings from one particular day and then apply those settings to otherdays of the week.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow chart of an illustrative method for programming amultiple-day schedule on a controller equipped with a user interface;

FIG. 2 is a flow chart of another illustrative method for programming amultiple-day schedule on a controller equipped with a user interface;

FIG. 3 is a block diagram of an illustrative HVAC system employing acontroller having multiple-day programming capabilities;

FIG. 4 is a plan view of an illustrative HVAC controller equipped with atouch screen interface;

FIGS. 5A-5J are pictorial views showing an illustrative method ofprogramming a multiple-day schedule using the touch screen interface ofFIG. 4;

FIG. 6 is a plan view of another illustrative HVAC controller equippedwith a display panel and keypad interface;

FIGS. 7A-7J are pictorial views showing an illustrative method ofprogramming a multiple-day schedule using the display panel and keypadinterface of FIG. 6;

FIG. 8 is a schematic view showing an illustrative embodiment forchanging set points across a schedule;

FIG. 9 is a schematic view showing another illustrative embodiment forchanging set points across a schedule;

FIG. 10 is a schematic view showing yet another illustrative embodimentfor changing set points across a schedule;

FIG. 11 is a schematic view showing an illustrative embodiment forchanging set points of a selected period across a schedule;

FIG. 12 is a schematic view showing an illustrative embodiment fordisplaying a number of device parameters of a schedule of a controller;

FIG. 13 is a schematic view showing another illustrative embodiment fordisplaying a number of device parameters of a schedule of a controller;

FIG. 14 is a schematic view showing yet another illustrative embodimentfor displaying a number of device parameters of a schedule of acontroller; and

FIG. 15 is a schematic view showing another illustrative embodiment fordisplaying a number of device parameters of a schedule of a controller.

DETAILED DESCRIPTION OF THE INVENTION

The following description should be read with reference to the drawings,in which like elements in different drawings are numbered in likefashion. The drawings, which are not necessarily to scale, depictillustrative embodiments and are not intended to limit the scope of theinvention. Although examples of various programming and operationalsteps are illustrated in the various views, those skilled in the artwill recognize that many of the examples provided have suitablealternatives that can be utilized. While the various devices, systemsand methods illustrated herein are described specifically with respectto HVAC controllers, it should be understood that the present inventioncan be employed in other applications where multiple-day schedules areimplemented, including, for example, water heater systems, watersoftener systems, security systems, lighting systems, sprinkler or dripwater systems, audio/video (A/V) systems, etc.

Referring now to FIG. 1, a flow chart showing an illustrative method ofprogramming a multiple-day schedule on a controller equipped with a userinterface is shown. The programming method, indicated generally byreference number 10, can begin with the step of initializing ascheduling routine within the controller that allows the user to viewand, if desired, modify various parameters within a schedule. In anillustrative HVAC system for use in a home, for example, the controllercan be configured to initialize a scheduling routine that allows theuser to view and modify one or more periods during the day correspondingwith the times during the day that the user wakes, leaves home, returnshome, and sleeps. For example, the controller may include a separate“wake” period, “leave” period, “return” period, and “sleep” period thatcan be programmed within the schedule to conserve energy while the useris away from home or asleep. The “wake” period, “leave” period, “return”period, and “sleep” period are only examples, and it is contemplatedthat any suitable schedule may be used, depending on the application.

Within each period, the controller can include various event time andset point parameters that can be utilized to regulate variousenvironmental conditions within a particular space. In certainembodiments, for example, the controller may include a heat set pointparameter and cool set point parameter that can be utilized to regulatethe amount of heating and/or cooling occurring within the home. Thecontroller may further include a fan mode parameter that can be set tooperate the fan in a particular manner during each period. For example,the controller can be configured to operate the fan constantly duringeach selected period (i.e. an “On Mode”), or automatically as needed(i.e. an “Auto Mode”) during each selected period. Other parameters suchas the ventilation, humidity level, frost level, air quality, etc. mayalso be regulated via the controller, as desired. The particularparameter(s) regulated by the controller will, of course, vary dependingon the type of system in which the device is employed.

From a normal controller operation mode indicated generally by block 12,the user may initialize a scheduling routine within the controller thatallows the user to view the current schedule parameters stored inmemory, and, if desired, modify one or more of the parameters to createa new schedule. To initialize the scheduling routine, the user may senda request to the controller via the user interface, causing thecontroller to initiate a schedule review mode that displays the currentsettings on the user interface. Initialization of the schedule reviewmode may occur, for example, when the user presses a button on a touchscreen or keypad, speaks a command, or otherwise sends a signal to thecontroller.

When the schedule review mode is initiated, the controller can beconfigured to display the current day and period settings for theschedule on the user interface, as indicated generally by block 14. Forexample, if the current time and day is 7:00 AM on Wednesday, thecontroller can be configured to display the “wake” period parameters forWednesday upon initiating the schedule review mode.

To view other selected days and/or periods within the current schedule,the user may select each day and/or period, causing the controller todisplay the parameters for the selected day and/or period on the userinterface, as indicated generally by block 16. The user can select eachday individually within the schedule review mode to view the scheduleparameters for each period without modification. If, for example, theuser is currently viewing the schedule parameters for Wednesday duringthe “wake” period, the user can select other individual days of the week(e.g. Tuesday) to view the schedule parameters for that day's “wake”period. Within each individual day selected, the user can select eachperiod to display the parameters scheduled to occur for that day. At anypoint during the schedule review mode, the user can send a signal to thecontroller to terminate the scheduling routine and return to the normalcontroller operation mode indicated by block 12.

In one illustrative embodiment, the user can modify one or more of theschedule parameters by initiating an editing mode within the controller.The user can initiate the editing mode by, for example, pressing an“edit” button on a touch screen, keypad or other input device, sending asignal to the controller to initiate the editing mode.

Upon initiation of the editing mode, the user interface can beconfigured to display a message that prompts the user to select the dayor days that are to be modified in the schedule. As indicated by block18, for example, the controller can be configured to display the message“OK TO PICK MULTIPLE DAYS” or other similar text or graphic on the userinterface, prompting the user to select those days in the schedule tomodify. The user can then select each day that is to be modified withinthe schedule, as desired.

As the first day is selected, the various periods in the schedule arethen displayed on the user interface, as indicated generally by block20. At this step, the user may select one or more days during the weekto modify the schedule. For example, the user may select to run theschedule on alternating days of the week, during only the weekdays orweekends, or any other desired combination. The controller can beconfigured to notify the user of each day or combination of daysselected using, for example, a check mark, blinking text, and/or othersuitable indicator on the user interface.

The controller can be configured to default to one of the periods uponselecting the first day, displaying the schedule parameters for thatparticular day and period on the user interface. For example, if theuser selects Monday as the first day to modify in the schedule, thecontroller can be configured to display the parameters for the “wake”period on the user interface. In certain embodiments, the controller canbe configured to default to the period last modified in the schedule, orto the period following the last period modified in the schedule. Inother embodiments, all periods for the selected day may be displayed.

Once the user has selected one or more days to be modified in theschedule, the controller can be configured to display the scheduleparameters scheduled for each individual period, as indicated generallyby block 22. The user can then modify one or more of the parameters foreach selected period, as desired, causing the controller to display thenew parameters on the user interface, as indicated generally by block24.

To modify the schedule parameters for other periods, the user can selecteach desired period individually, and then repeat the process againuntil all desired periods have been modified in the schedule. In somecases, the user can select more than one period at once in order tosimultaneously modify at least some of the parameters, such as the setpoints, at the selected periods and across the selected days. At anytime during this process, the user may select or deselect one or moredays of the week to include/exclude the modified parameters. Forexample, if the user decides after initially modifying the scheduleparameters for one or more periods of selected days of the week, theuser may select an additional day to include the modified scheduleparameters. If desired, the user may choose to cancel the modifiedparameters by hitting a “cancel” button or other similar command on theuser interface, causing the controller to terminate the scheduleroutine, discard the modified parameters, and return to the normalcontroller operation mode indicated by block 12.

The process of selecting the parameters for each period can be easilyapplied to one or more selected days during the week without having tofirst copy settings from one particular day, and then apply thosesettings to other selected days. For example, if the user has previouslyselected only Monday and Wednesday, but later decides to add Friday tothe schedule, the user can send a signal to the controller to selectFriday at any step during the editing routine to apply the modifiedschedule parameters for Friday. Since days can be easily selected orde-selected via the user interface, the user is not required to copy thesettings for a particular day, and then apply those settings for theother days. Moreover, since the user can select any day or combinationof days via the user interface, greater flexibility is provided tocreate a customized schedule.

After the user has finished modifying the schedule, the user can send asignal to the controller to either save or discard the modifiedsettings. As indicated generally by block 26, the controller can beconfigured to display the text “Saving Changes” or other similar messageon the user interface to notify the user that the controller has savedthe modified schedule parameters. Once the modified schedule parametershave been either saved or cancelled, the controller can be configured toterminate the scheduling routine and revert to the normal controlleroperation mode indicated by block 12. Alternatively, and as shown bydashed line 28, the controller may revert back to, for example, block 18to allow the user to select another day or set of days, as desired. Oncesaved, the controller can be configured to automatically run themodified schedule.

FIG. 2 is flow chart of another illustrative method for programming amultiple-day schedule on a controller equipped with a user interface.The programming method, indicated generally by reference number 30, canbegin with the step of initializing a scheduling routine within thecontroller that allows the user to view and, if desired, modify variousparameters within the schedule. As with the illustrative embodiment ofFIG. 1, the user may initialize the scheduling routine from a normaloperation mode 32, causing the controller to display the current day andperiod settings for the schedule on the user interface, as indicatedgenerally by block 34. To view other selected days and/or period(s)within the current schedule, the user may select each day and/or periodon the user interface, causing the controller to display the parametersfor the selected day and/or period on the user interface, as indicatedgenerally by block 36.

In one illustrative embodiment, the user can modify one or more of theschedule parameters by initiating an editing mode within the controller.The user can initiate the editing mode by, for example, pressing an“edit” button on a touch screen, keypad or other input device, sending asignal to the controller to initiate the editing mode.

Upon initiation of the editing mode, the user interface can beconfigured to display a message that prompts the user to select one ormore days and/or one or more periods that can be modified in theschedule. As indicated by block 38, for example, the controller can beconfigured to display the message “OK TO PICK ONE OR MORE PERIODS AND/ORDAYS” or other similar text or graphic on the user interface, promptingthe user to user to select one more days and/or periods to be modifiedwithin the schedule, as desired.

As the first period and/or day is selected, the various period(s) and/orday(s) to be modified are then displayed on the user interface, asindicated generally by block 40. At this step, the user may select anycombination of days and/or periods to modify the schedule, as desired.For example, the user may select to run the schedule on multiple daysfor a certain period, for a single day with multiple periods, or formultiple days with multiple periods for each selected day. Thecontroller can be configured to notify the user of each day and/orperiod selected using, for example, a check mark, blinking text, and/orother suitable indicator on the user interface.

Once the user has selected one or more periods and/or days to bemodified in the schedule, the controller can be configured to displaythe schedule parameters scheduled for the selected period(s) and/orday(s), as indicated generally by block 42. The user can then modify oneor more of the schedule parameters, as desired, causing the controllerto display the new parameters on the user interface, as indicatedgenerally by block 44. At any time during this process, the user mayselect or de-select one or more periods and/or days of the week to runthe schedule without modifying the schedule parameters. If desired, theuser may choose to cancel the modified parameters by hitting a “cancel”button or other similar command on the user interface, causing thecontroller to terminate the scheduling routine, discard the modifiedparameters, and return to the normal controller operation mode indicatedby block 32.

Once the user has finished modifying the schedule, the user can send asignal to the controller to save the modified settings, as indicatedgenerally by block 46. In certain embodiments, the controller can beconfigured to display the text “Saving Changes” or other similar messageon the user interface to notify the user that the controller has savedthe modified schedule parameters. Once the modified schedule parametershave been either saved or cancelled, the controller can be configured toterminate the scheduling routine and revert to the normal controlleroperation mode indicated by block 32. Alternatively, and as shown bydashed line 48, the controller may revert back to, for example, block 38to allow the user to select one or more additional periods and/or days,as desired. Once saved, the controller can be configured toautomatically run the modified schedule.

FIG. 3 is a block diagram of an illustrative HVAC system 50 employing acontroller 52 having multiple-day programming capabilities. Theillustrative controller 52 includes a processor 54 (e.g. amicroprocessor/CPU), a storage memory 56, a clock 58, and an I/Ointerface 60 that electrically connects the controller 52 to othersystem components 62. In an illustrative HVAC system for use in a home,the controller 52 can be electrically connected to an air conditionerunit, heater unit, ventilation unit, and/or a humidifier/dehumidifierunit that can be selectively activated or deactivated to regulate thetemperature, humidity and air quality levels within the home. Othercomponents such as a filtration unit, UV lamp, defroster, and fluedamper can also be connected to the controller 52, as desired. Aninternal sensor 64 may be located within the controller 52, and can beemployed to constantly measure the temperature and/or humidity levelsoccurring within the structure. In certain designs, the controller 52can include one or more remote sensors (not shown) configured to measurethe temperature and humidity levels outside of the home, or at locationsapart from the controller 52.

The controller 52 can be equipped with a user interface 66 that can beused to transmit signals to and from the controller 52. The userinterface 66 can include a touch screen, LCD panel and keypad, dotmatrix display, computer (e.g. a PDA), or any other suitable device forsending and receiving signals to and from the controller 52. In certainembodiments, the user interface 66 may include a menu-driven interfacethat allows the user to cycle through one or more menus or screens toview and, if desired, modify various operational settings within thecontroller 52. For example, the controller 52 can be pre-programmed torun separate routines for adjusting the current temperature or humiditylevels, changing the clock or date settings on the controller 52,setting a vacation mode on the controller 52 that can be run while theuser is away, or checking the status of the various system componentsconnected to the controller 52. The menus or screens corresponding to aparticular routine can be organized from general to more specific,providing the user with only pertinent information at each step withinthe routine.

FIG. 4 is a plan view illustrating an exemplary HVAC controller 68equipped with a user interface 70 suitable for programming amultiple-day schedule. As shown in FIG. 4, the user interface 70 caninclude a touch screen 72 configured to display information and transmitsignals to and from the controller 68. Some examples of suitable touchscreens for use with the controller 68 may include resistive,capacitive, infrared or surface acoustic wave (SAW) type touch screens.While the touch screen 72 of FIG. 4 is shown inset or recessed within acontroller housing 74, other configurations are possible. In someembodiments, the touch screen 72 may be provided as a separate elementfor use with a personal digital assistant (PDA), PC computer, or otherremote device. In certain embodiments, the touch screen 72 can beprovided as part of a liquid crystal display (LCD) panel, cathode raytube (CRT), or other suitable display device.

FIGS. 5A-5J are pictorial views showing an illustrative method ofprogramming a multiple-day schedule using the controller 68 and userinterface 70 of FIG. 4. In a first view depicted in FIG. 5A, thecontroller 68 can be configured to display a main menu screen 76 on thetouch screen 72, providing the user with basic information about thecurrent operational status of the controller 68. The main menu screen 76may be the default screen that appears on the touch screen 72 when thecontroller 68 is initially activated, after a loss of power hasoccurred, or after no activity has been detected by the user interface70 for a certain period of time (e.g. after 1 minute of non-activity).

In the illustrative embodiment, the controller 68 is configured todisplay a current inside temperature parameter 78 (in either ° F. or °C.), a current outside temperature parameter 80 (in either ° F. or °C.), a time of day parameter 82, and a day of week parameter 84 on thetouch screen 72. The current heat/cool set point parameter 86 may alsobe displayed on the touch screen 72, indicating the temperature at whichthe controller 68 is currently set to maintain. An alphanumeric message88 displayed on the touch screen 72 may be provided to inform the userwhether the controller 68 is currently following the schedule.

A set of up/down buttons 90 displayed on the touch screen 72 can bepressed, if desired, to temporarily change the current heat/cool setpoint parameter 86 to a setting different from that contained in theschedule. A fan mode button 92 and system mode button 94 displayed onthe touch screen 72 allow the user to view and, if desired, modify thefan and system settings. For example, and in the illustrativeembodiment, the fan mode button 92 can be pressed repeatedly to cyclethe fan between an “On Mode”, “Auto Mode”, and other modes as desired,allowing the user to control the operation of the fan. In similarfashion, the system mode button 94 can be pressed repeatedly to cyclethe controller 68 through various heating and cooling modes, as desired.

A “SCHED” button 96 located on the main menu screen 76 can used toinitialize a scheduling routine within the controller 68 to modify oneor more parameters within the current schedule. When the “SCHED” button96 is pressed, the controller 68 can be configured to initiate aschedule review mode, causing the controller 68 to access the currentschedule parameters and display them on the touch screen 72. As shown inFIG. 5B, for example, the controller 68 can be configured to access theevent time parameter 98, heat set point parameter 100, and cool setpoint parameter 102 for the current schedule, and then display theseparameters as alphanumeric text on the touch screen 72.

In the illustrative embodiment, a series of buttons 104 located on thetop of the touch screen 72 correspond to the days of the week, and canbe pressed to send a signal to the controller 68 to display the scheduleparameters for each individual day in the schedule. An icon, blinkingtext or other suitable indicator for informing the user the current dayselected may be displayed on the touch screen 72. For example, in thepictorial view illustrated in FIG. 5B, an icon 106 (e.g. check mark) maybe displayed on the touch screen 72, informing the user that theschedule parameters for Wednesday are currently being displayed.

The controller 68 can be configured to default to the current day of theweek when the schedule review mode is initiated. For example, if thecurrent time and day is 7:00 AM on Wednesday, the controller 68 can beconfigured to display the “wake” period parameters for Wednesday on thetouch screen 72. To view the schedule parameters for other days of theweek, the user may press the appropriate day button 104 on the touchscreen 72, causing the controller 68 to display the correspondingparameters for that selected day.

Within each selected day, the user may press one or more period buttonson the touch screen 72, causing the controller 68 to display theparameters scheduled for that day. The touch screen 72 may include, forexample, a “WAKE” button 108, a “LEAVE” button 110, a “RETURN” button112, and a “SLEEP” button 114 that correspond to a separate “wake”period, “leave” period, “return” period, and “sleep” period programmedin the controller 68. In the pictorial view depicted in FIG. 5B, forexample, the “LEAVE” button 110 has been pressed (indicated generally bybolded text), causing the controller 68 to display the event timeparameter 98 (i.e. 8:00 AM), heat set point parameter 100 (i.e. 62° F.)and cool set point parameter 102 (i.e. 85° F.) corresponding to the“leave” period.

While four periods are specifically illustrated in FIG. 5, it should beunderstood that the controller 68 could be programmed for a greater orlesser number of periods, if desired. The number of periods will, ofcourse, vary depending on the particular application in which thecontroller 68 is employed.

Once the user has finished viewing the desired schedule parameters foreach day and/or period, the user can terminate the schedule review modeby pressing a “DONE” button 116 or “CANCEL” button 118 displayed on thetouch screen 72, causing the controller 68 to terminate the schedulingroutine and return to the main menu screen 76 of FIG. 5A.

To modify one or more parameters in the schedule, the user can initiatean editing mode within the controller 68 by pressing an “EDIT” button120 on the touch screen 72. As shown in FIG. 5C, for example, if theuser presses the “EDIT” button 120, an alphanumeric message 122 stating,for example “OK TO PICK MULTIPLE DAYS” can appear on the touch screen72, informing the user that multiple days can be selected. Other messagevariations may appear in addition to, or in lieu of, the alphanumericmessage 122 illustrated in FIG. 5C. For example, the controller 68 canbe configured to display the text “PLEASE SELECT AT LEAST ONE DAY TOMODIFY” or other similar message on the touch screen 72. The user canthen either select one or more days to modify the schedule using theappropriate day button(s) 104, or press the “CANCEL” button 118 toterminate the scheduling routine and return to the main menu screen 76of FIG. 5A.

FIG. 5D is a pictorial view showing the selection of Monday, Tuesday,and Thursday using the “MON”, “TUE” and “THU” buttons 104 on the touchscreen 72. As shown in FIG. 5D, when at least one of the day buttons 104is pressed, the controller 68 can be configured to display the currentlyprogrammed event time parameter 98, heat set point parameter 100, and acool set point parameter 102 for one of the periods in the schedule. Aset of up/down buttons 124 can be utilized to modify the event timeparameter 98 within the schedule to an earlier or later time, asdesired. A similar set of up/down buttons 126,128 can be utilized toadjust, respectively, the heat set point parameter 100 and cool setpoint parameter 102 to a higher or lower temperature level, as desired,for the selected period.

The controller 68 can be configured to indicate the particular periodthe user is viewing on the touch screen 72 using an icon, blinking textor other indicator means. In FIG. 5D, for example, the text for the“WAKE” button 108 can configured to blink on and off (indicatedgenerally by bolded text) to indicate that the user is currently viewingthe settings for the “wake” period.

If the user desires to modify one or more of schedule parameters for theselected period, the user may use the appropriate set of up/down buttons124,126,128 to modify the parameter. As shown in FIG. 5E, for example,the user can modify the event time parameter 98 from 6:00 AM to 6:30 AMusing the set of up/down buttons 124 located adjacent to the event timeparameter 98. In similar fashion, the user may use the appropriate setof up/down buttons 126,128 to adjust the heat set point parameter 100from 70° F. to 72° F., and the cool set point parameter 102 from 78° F.to 76° F.

To display the parameters for the other periods, the user may press theappropriate period button on the bottom of the touch screen 72, causingthe controller 68 to display the schedule parameters for that selectedperiod. To display the settings for the “leave” period, for example, theuser may press the “LEAVE” button 110 on the touch screen 72, causingthe controller 68 to display the event time parameter 98, heat set pointparameter 100, and cool set point parameter 102 for the “leave” periodon the touch screen 72, as shown in FIG. 5F. Once selected, theappropriate set of up/down buttons 124,126,128 can be pressed to modifythe scheduler parameters, as desired. As with the “WAKE” button 108discussed above with respect to FIG. 5E, the “LEAVE” button 110 caninclude indicator means (e.g. blinking text) to indicate that that theuser is currently viewing the settings for the “leave” period.

FIGS. 5G and 5H are pictorial views showing the schedule parameterscorresponding, respectively, to the “return” and “sleep” periods of theschedule. In FIG. 5G, for example, the “RETURN” button 112 has beenselected (indicated generally by bolded text), causing the controller 68to display the event time parameter 98 (i.e. 6:00 PM), heat set pointparameter 100 (i.e. 70° F.) and cool set point parameter 102 (i.e. 78°F.) on the touch screen 72. In similar fashion in FIG. 5H, the “SLEEP”button 114 has been selected, causing the controller 68 to display theevent time parameter 98 (i.e. 11:00 PM), heat set point parameter 100(i.e. 62° F.), and cool set point parameter 102 (i.e. 82° F.) for the“sleep” period on the touch screen 72. Once selected, the user may thenadjust the schedule parameters using the appropriate set of up/downbuttons 124,126,128 on the touch screen 72, as desired.

In the illustrative embodiment, the user may select or de-select one ormore days at any point during the editing mode using the appropriate daybutton(s) 104 located on the touch screen 72. In the illustrative viewof FIG. 5H, for example, the user may desire to add “Wednesday” to thelist of days to run the modified schedule parameters. To do so, the usermay press the “WED” button 104 on the touch screen 72, causing thecontroller 68 to add that day to the modified schedule. Conversely, ifthe user desires to remove one or more days from the modified schedule,the user may simply press the appropriate day button 104 on the touchscreen 72, causing the controller 68 to remove those day(s) from themodified schedule.

If the user desires to cancel a particular period from the schedule, theuser can select the appropriate period button 108,110,112,114 and thenpress a “CANCEL PERIOD” button 130 on the touch screen 72. As shown inFIG. 5I, for example, when the user presses the “CANCEL PERIOD” button130 while in the “wake” period, the controller 68 can be configured tocancel or zero-out the event time parameter 98, heat set point parameter100, and/or cool set point parameter 102 for that period. An icon 132normally situated above the “WAKE” button 108 can be configured todisappear on the touch screen 72, indicating to the user that theschedule parameters for that particular period have been cancelled. Whenthe modified schedule is subsequently run, the controller 68 can beconfigured to apply the settings for the previous period towards thecancelled period until the next scheduled period occurs.

After the user has finished modifying the schedule, the user can presseither the “DONE” button 116 to save the modified parameters in theschedule, or the “CANCEL” button 118 to discard the modified changeswithout saving. As shown in FIG. 5J, the controller 68 can be configuredto temporarily display an alphanumeric message 134 such as “SAVINGCHANGES” on the touch screen 72 at or near the time that the controller68 saves the modified settings. The controller 68 can also be configuredto temporarily display the days of the week on the touch screen 72 toconfirm the selected days modified in the schedule. In some embodiments,the controller 68 can be configured to revert back to the main menuscreen 76 of FIG. 5A and, if desired, automatically run the modifiedschedule.

FIG. 6 is a plan view illustrating another exemplary HVAC controller 136equipped with a user interface 138 suitable for programming amultiple-day schedule. In the illustrative embodiment of FIG. 6, theuser interface 138 includes a display panel 140 and keypad 142 equippedwith a number of buttons that can be pressed by the user to scrollthrough various menus or screens displayable on the display panel 140.Display panel 140 can include any number of suitable display devices,including, for example, a backlit LCD panel or LED screen.

FIGS. 7A-7J are pictorial views showing an illustrative method ofprogramming a multiple-day schedule using the controller 136 andinterface 138 of FIG. 6. In a first view depicted in FIG. 7A, thecontroller 136 can be configured to display a main menu screen 144 onthe display panel 140, similar to that described above with respect toFIG. 5A. The controller 136, for example, can be configured to display acurrent inside temperature parameter 146 (in either ° F. or ° C.), atime of day parameter 148, and a day of week parameter 150. Thecontroller 136 can also be configured to display the current set pointparameter 152 on the display panel 140, indicating the temperature atwhich the controller 136 is currently set to maintain. A set of up/downbuttons 154 on the keypad 142 can be used to scroll through the variousschedule parameters displayed on the display panel 140. A second seriesof buttons 156,158,160 disposed below the display panel 140 can beutilized to navigate through one or more menus or screens displayable onthe display panel 140.

To initialize the scheduling routine within the controller 136, the usermay press the button 158 located immediately below the text “SCHEDULE”located on the display panel 140. When pressed, the controller 136 canbe configured to initiate a schedule review mode, causing the displaypanel 140 to display each day of the week, as shown in FIG. 7B. Usingthe up/down buttons 154, the user can scroll up or down between each dayof the week. As each day is selected, the controller 136 can beconfigured to blink or otherwise indicate the day of the week that hasbeen selected. The user can then press the button 156 located below thetext “GO BACK” on the display panel 140 to go back to the previousscreen (i.e. main screen 144), or buttons 158 or 160 to initiate,respectively, the editing and schedule review modes within thecontroller 136.

FIG. 7C is a pictorial view showing display panel 140 after “Monday” hasbeen selected using the up/down buttons 154, and after button 160 hasbeen pressed. As shown in FIG. 7C, for example, the controller 136 canbe configured to display the event time parameter 162 and heat/cool setpoint parameter 164 for each individual period in the schedule. In FIG.7C, for example, the various schedule parameters for each period candisplayed on the display panel 140 by repeatedly pressing the up/downbuttons 154 on the keypad 142, causing the controller 136 to scrollthrough each individual period on the display panel 140. When the useris finished viewing the schedule parameters for that particular day, theuser may either press button 156 to go back to the previous screen (seeFIG. 7B), or button 160 to go back to the main screen 144 (see FIG. 7A).

To modify one or more parameters in the schedule, the user can initiatean editing mode within the controller 136. The user can modify theschedule either individually on a day-by-day basis from within theschedule review mode, or directly via the screen illustrated in FIG. 7Bby bypassing the schedule review mode.

To edit the parameters on a day-by-day basis, the user, while within theschedule review mode, may select the individual day of the week tomodify, and then press button 158 located below the text “Edit” locatedon the display panel 140 (see FIG. 7C). For the day “Monday” selected inFIG. 7C, for example, the user can press button 158 while viewing thevarious parameters for the “wake” period, causing the controller 136 toinitiate the editing mode and display the parameters for that specificday, as shown in FIG. 7D. A check mark 166, blinking text, or othersuitable indicator can be configured to appear on the display panel 140,indicating that the user has selected to modify the parameters forMonday.

The controller 136 can be configured to prompt the user to cycle throughthe various schedule parameters for each period by blinking the text forthe selected schedule parameter on the display panel 140. For example,the event time parameter 162 in FIG. 7D can be configured to blink onand off, indicating that the user can modify that particular parameterusing the up/down buttons 154 on the keypad 142. The user may thenchange the event time parameter 162 to, for example, 6:30 AM byrepeatedly pressing the appropriate one of the up/down buttons 154 until6:30 AM appears on the display panel 140.

To change the other parameters for that selected period, the user canpress button 158 located immediately below the text “Next Step” on thedisplay panel 140, causing the controller 136 to cycle to the nextschedule parameter in that period. As the user cycles through eachschedule parameter, the controller 136 can be configured to blink theappropriate text on the display panel 140, as shown in FIGS. 7E-7F. Whenthe user has cycled through each schedule parameter for the selectedperiod, the user may press button 158 again, causing the controller 136to cycle to the next period in the schedule. The process of selectingand modifying schedule parameters can then be repeated, as desired,until all of the parameters for each and every period have beenselected. At any point during this process, the user can save themodified settings by pressing button 160 located under the text “Done”on the display panel 140, causing the controller 136 to save themodified schedule parameters.

To select multiple days to program at once in the illustrativeembodiment, the user can initiate the editing mode directly from thescreen depicted in FIG. 7B by pressing button 158 located under the text“Edit” on the display panel 140. When button 158 is pressed, thecontroller 136 can be configured to display the text “Select Day” abovebutton 156, prompting the user to select one or more days to modify inthe schedule. Using the up/down buttons 154 and the “select day” button156, the user can scroll through each day of the week and, if desired,select individually each day of the week to modify in the schedule (e.g.Monday, Tuesday, and Thursday), as shown, for example, in FIG. 7G. Acheck mark 168, blinking text or suitable indicator can be displayed onthe display panel 140 next to each day selected, indicating those daysof the week to be modified in the schedule.

Once the user has selected the desired day or days to modify theschedule, the user can then press the “Next Step” button 158, causingthe controller 136 to display the schedule parameters for one period. Asshown in FIG. 7H, for example, the controller 136 can be configured toblink the text “Wake” on the display panel 140 (indicated generally bybolded text), indicating that the parameters for the “wake” period canbe modified using the up/down buttons 154 and the “next/step” button158, similar to that described above with respect to FIGS. 7D-7F. Asshown in FIG. 7I, the user can press button 158 repeatedly until thedisplay panel 140 indicates (by blinking text) that the cool set pointparameter 164 has been selected. Using the up/down buttons 154, the usercan then modify the cool set point parameter 164 to a higher or lowervalue, as desired.

When the user has cycled through each of the parameters for a particularperiod, the user may press button 158 again, causing the controller 136to cycle to the next period in the schedule. The process of selectingand modifying the parameters can then be repeated, as desired, until allof the parameters for each period have been selected and modified (ifdesired). At any point during this process, the user can save themodified settings by pressing button 160 located under the text “Done”on the display panel 140, causing the controller 136 to save themodified schedule parameters.

As shown in FIG. 7J, the controller 136 can be configured to temporarilydisplay an alphanumeric message 170 such as “SAVED” on the display panel140 at or near the time that the controller 136 saves the modifiedsettings. The controller 136 can also be configured to temporarilydisplay the days of the week on the display panel 140 to confirm to theuser the particular days of the week modified in the schedule. In someembodiments, the controller 136 can revert back to the main menu screen144 of FIG. 7A, and, if desired, automatically run the modifiedschedule.

FIG. 8 is a schematic view showing another illustrative embodiment forchanging a selected set point value from a current value to a new valueacross a schedule. An illustrative weekly schedule for an HVACcontroller is shown at 180, and an illustrative user interface is shownat 182. In the illustrative embodiment, the user is allowed to select acurrent set point value to change using a current set point selectionbox 184. The user is also allowed to select a new set point value usingnew set point selection box 186. In the illustrative embodiment, theHVAC controller may search though the set points in the schedule 180,and replace all of the set points in the schedule 180 that have thecurrent value with the new set point value, regardless of the positionwithin the schedule 180.

In some embodiments, the user interface 182 may also allow a user toselect certain days (and/or period—e.g. Wake, Leave, Return, Sleep), asgenerally shown at 190. When so provided, the HVAC controller may searchthrough the set points on the selected days (and/or periods) of theschedule 180, and replace those set points that have the current valuewith the new set point value.

In the example shown, and referring to user interface 182, the user hasselected a current set point value of 70 degrees via current set pointselection box 184, a new set point value of 72 degrees via new set pointselection box 186, and days Tuesday, Wednesday, Thursday and Friday viadays selection boxes generally shown at 190. In response, the HVACcontroller may replace all set points on Tuesday, Wednesday, Thursdayand Friday of the schedule 180 that have a value of 70 degrees with anew value of 72 degrees, regardless of the period (e.g. Wake, Leave,Return and Sleep periods). The set points to be updated to 72 degrees inthis example are highlighted with a circle in the schedule 180. As notedabove, and in some embodiments, the user interface 182 may allow a userto select one or more periods (e.g. Wake, Leave, Return and Sleepperiods) rather than days, or in addition to days, as desired. In anyevent, the illustrative embodiment of FIG. 8 may reduce or eliminate theneed to scroll through each day and/or period of the schedule, and makeindividual changes to the set points.

FIG. 9 is a schematic view showing another illustrative embodiment forchanging set points across a schedule. FIG. 9 shows an illustrativeweekly schedule 200 for an HVAC controller, an illustrative userinterface 202 for setting heat set points, and an illustrative userinterface 204 for setting cool set points. While the user interface 202and 204 are shown as separate interfaces, it is contemplated they may becombined into one user interface, if desired.

In this illustrative embodiment, the set points in the schedule 200 areset to a tag or pointer value, rather than a temperature value. Forexample, the set points in the schedule 200 are set to tag or pointervalue of High “H”, Medium “M” or Low “L”, corresponding to a high setpoint value, a medium set point value and a low set point value,respectively. A user interface, such as user interface 202, may then beused to assign and/or change a temperature value that is associated witheach tag or pointer value. In the illustrative user interface 202 ofFIG. 9, a value of 73 degrees has been assigned to the High “H” heat setpoint, a value of 71 degrees for the Medium “M” heat set point, and avalue of 68 degrees for the Low “L” heat set point. In the illustrativeembodiment, the user interface 204 may be used to assign cool set pointsin a similar manner. When operating in accordance with the schedule 200,the HVAC controller may read up the appropriate tag or pointer value,and set the current set point to the temperature assigned thereto.

By using a tag or point value, rather than a temperature value for theset points in the schedule 200, the user may more easily change a setpoint across the schedule. For example, in the illustrative embodiment,by changing the value assigned to the High “H” heat set point 206 from73 degrees to 75 degrees, all of the heat set points with a tag orpointer value of high “H” may be changed across the schedule 200. Thismay help reduce or eliminate the need to scroll through each day and/orperiod of the schedule, and make individual changes to the set points.

FIG. 10 is a schematic view showing yet another illustrative embodimentfor changing set points across a schedule. FIG. 10 shows an illustrativeweekly schedule 210 for an HVAC controller, and an illustrative userinterface at 212. In this illustrative embodiment, the user interface212 allows a user to input an offset value 214. The offset value 214 maybe used to offset at least some of the set point values in the schedule210. In some embodiments, all of the set point values in the schedule210 are offset by the specified amount. In other embodiments, only thoseset points that are on selected days 216 and/or in selected periods(e.g. Wake, Leave, Return and Sleep), as desired. Also, and in someembodiments, the offset 214 may only be applied to “heat” set points, oronly to “cool” set points, depending on the application. Again, this mayhelp reduce or eliminate the need to scroll through each day and/orperiod of the schedule, and make individual changes to the set points.

FIG. 11 is a schematic view showing an illustrative embodiment forchanging set points of a selected period across a schedule. FIG. 11shows an illustrative weekly schedule 220 for an HVAC controller, and anillustrative user interface at 222. In this illustrative embodiment, theuser interface 222 allows a user to select a desired period (e.g. Wake,Leave, Return and Sleep) 224 from the schedule 220, as well as a new setpoint value 226. In some embodiments, the user interface 222 may alsoallow the user to select one or more days of the schedule, as shown at228. Once selected, the set points for the selected period, and possiblyfor the selected days, may be updated to the new set point value. In theexample shown, the “Wake” period has been selected at 224, a new heatset point value of 73 degrees has been selected at 226, and days Tuesdaythrough Saturday have been selected at 228. In this example, the heatset points for the “Wake” period on Tuesday through Saturday may bechanged to 73 degrees. The set points that will be updated to 73 degreesin this example are highlighted by a circle in the schedule 220. As canbe seen, this may also help reduce or eliminate the need to scrollthrough each day and/or period of the schedule, and make individualchanges to the set points.

In some cases, it may be desirable to display some, many or all of theparameters of a schedule on a single or limited number of screens. Thismay help a user to get a more complete picture of the schedule withouthaving to traverse many different display screens. FIG. 12 is aschematic view showing an illustrative embodiment for displaying anumber of schedule parameters of a controller. The illustrative display250 includes a number of schedule period rows including a “wake” periodrow 252, a “leave” period row 254, a “return” period row 256 and a“sleep” period row 258. It should be recognized that these are onlyillustrative schedule periods, and that any suitable schedule period maybe used, as desired.

The illustrative display 250 also shows a number of day columns. Only aMonday column 260 and part of a Tuesday column 262 are shown on theillustrative display 250. However, in the illustrative embodiment, theschedule may also include day columns for the other days of the week. Anumber of schedule parameters are shown under each day column. Forexample, the Monday column 260 includes a “time” column 264 that showsthe time that the corresponding schedule period begins, an “H” column266 that shows the heat set point for the corresponding schedule period,a “C” column 268 that shows the cool set point for the correspondingschedule period, and a “FAN” column 270 that shows the fan mode for thecorresponding schedule period. In the illustrative embodiment, the daycolumns for the other days of the week (not shown) may include the sameor similar schedule parameter columns, if desired. It should berecognized that these schedule parameter columns are only illustrative,and that different programmed schedule parameters may be used asdesired.

In one illustrative embodiment, the display 250 allows the user mayscroll or pan across the controller schedule using scroll or pan buttons280 and 282. For example, the user may press the right scroll or panbutton 282 to move the display in a rightward direction relative to thecontroller schedule to display, for example, the rest of the Tuesday daycolumn 262. When this occurs, some or all of the Monday day column 260may fall off the left of the display and no longer be displayed. Theuser may again press the right scroll or pan button 282 to display allor part of the Wednesday day column (not shown). This may be repeated toview the entire schedule of the controller. At any time, the user maypress the scroll or pan button 280 to scroll or pan back through theschedule in a leftward direction, as desired. The amount that thedisplay travels relative to the controller schedule with each push ofthe scroll or pan buttons 280 and 282 may depend on the application, andin some cases, set by the user. For example, the display may travel aportion of a day column, an entire day column, or more than one daycolumn with each push of the scroll or pan buttons 280 and 282.

In some embodiments, part of the display may remain stationary as thescroll or pan buttons 280 and 282 are pressed. For example, the “Wake”,“Leave”, “Return” and “Sleep” designators shown at 252, 254, 256 and 258may remain stationary on the display 250. Likewise, the scroll or panbuttons 280 and 282 may remain stationary, as well as other controlbuttons, as desired.

In some embodiments, the user may select a particular parameter or setof parameters for modification. In the illustrative embodiment, the usermay select, for example, the heat set point 290 for the wake period onMonday. The user may select the particular parameter in any number ofways. For example, if the display 250 is a touch screen, the user maysimply touch the particular parameter. If the display 250 is not a touchscreen, one or more navigation buttons (not shown) may be used totraverse and select various parameters of the schedule. Once selected,the user may edit the parameter, if desired. For example, and in theillustrative embodiment, the user may press the edit button 292 to enteran edit mode. Then, one or more up/down buttons (not shown) or the likemay be used to change the value of the selected schedule parameter.

The schedule may appear to be one continuous schedule extending fromMonday through Sunday, with the display 250 appearing as a “window” thatdisplays only a portion of the schedule. The scroll or pan buttons 280and 282 may be used to move the display “window” across the schedule. Itis believed that this may provide an intuitive interface that may help auser can get a more complete picture of the schedule without having totraverse many different display screens.

FIG. 13 is a schematic view showing another illustrative embodiment fordisplaying a number of device parameters of a schedule of a controller.In this illustrative embodiment, the display 300 shows a subset of theschedule parameters, but not all of the schedule parameters. Referringto FIG. 13, and in the illustrative embodiment, only the heat and coolset points are shown for each schedule period (e.g. wake, leave, return,sleep) and for each day. In some cases, this amount of information mayfit onto a single screen of a controller. While the heat and cool setpoints may provide the user with a good overall picture of the currentlyprogrammed schedule, it is contemplated that any subset of the scheduleparameters may be chosen for display. Also, and in some embodiments, theuser may select which subset of the schedule parameters are selected fordisplay.

To view additional schedule parameters, and in the illustrativeembodiment, the user may select a particular schedule period and day.For example, and in FIG. 13, the user has selected the “Wake” period forMonday, as highlighted by dark box 302. When selected, the illustrativedisplay may provide a pop-up window 304 that displays some or all of theschedule parameters for that period/day. In some embodiments, a showbutton 308 or the like may be provided to cause the display to providethe pop-up window 304, although this is not required or even desired inall embodiments.

In some embodiments, the user may select a particular schedule parameterin the pop-up window 304 for editing. For example, the user may selectthe Wake Start Time 306 for editing. Once selected, the user may changethe value of the Wake Start Time, as desired. Again, it is believed thatthis may provide an intuitive interface that may help a user get a morecomplete picture of the schedule without having to traverse manydifferent display screens.

FIG. 14 is a schematic view showing yet another illustrative embodimentfor displaying a number of device parameters of a schedule of acontroller. In this illustrative embodiment, a controller schedule isshown in a graphical format. The time of day extends from left to right,beginning at 1 AM and ending to 12 AM. In the illustrative embodiment,vertically extending dashed lines are provided to show the beginning ofeach hour of the day.

Each of the seven days of a week is shown along the left of the graph.While seven days are shown, it is contemplated that fewer or more daysmay be provided, or groups of days, or other time periods, may beprovided depending on use. Each of the seven days includes a line graphthat indicates when each of a number of schedule time periods begins. Inthe illustrative embodiment, “wake”, “leave”, “return” and “sleep” timeperiods are available for each day. However, it should be recognizedthat other schedule time periods may be used, if desired.

Referring the line graph 330 for Monday, the “sleep” time period beginsat 12:00 AM as indicated at 330 a, the “wake” time period begins at 4:00AM as indicated at 330 b, the “leave” time period begins at 8:00 AM asindicated at 330 c and the “return” time period begins at 6:00 PM asindicated at 330 d. In the illustrative embodiment, the height of theline graph only indicates a relative temperature (e.g. comforttemperature versus energy saving temperature), and does not indicate anactual temperature set point. Instead, the heat set point, fan setting,and other parameters may be shown adjacent to the line graph in each orselected schedule periods. For example, and in the illustrativeembodiment, designations “68” “A” are provided adjacent to the linegraph during the “sleep” period. The designation “68” indicates that theheat set point is set to 68 degrees, and the designation “A” indicatesthat the fan mode is set to AUTO. Similar designations may be providedfor the “wake”, “leave” and “return” schedule time periods, as shown.Although not explicitly shown, cool set points and/or other scheduleparameters may be provided on the display. Also, in some embodiments,the height of the line graph may provide a measure of, for example, aset point temperature. That is, the horizontal lines of the line graph330 may be positioned along a vertical temperature scale provided forline graph 330 so that the vertical position of each horizontal segmentprovides an indication of the heat set point or some other scheduleparameter of the schedule. Alternatively, or in addition, the color ofgraph segments may provide an indication of the value of the scheduleparameter (e.g. set point temperature). It is believed that thisembodiment may also provide an intuitive interface that may help a userget a more complete picture of the schedule without having to traversemany different display screens.

FIG. 15 is a schematic view showing another illustrative embodiment fordisplaying a number of device parameters of a schedule of a controller.Like above, and in this illustrative embodiment, a controller scheduleis shown in a graphical format. The time of day extends from left toright, beginning at 1 AM and ending to 12 AM. In the illustrativeembodiment, vertically extending dashed lines are provided to show thebeginning of each hour of the day.

Each of the seven days of a week is shown along the left of the graph.While seven days are shown, it is contemplated that fewer or more daysmay be provided, or groups of days, or other time periods, may beprovided depending on use. In the illustrative embodiment, each of theseven days includes two linear line graphs, each having a number ofsegments. The upper linear line graph corresponds to the programmed coolset point, and the lower linear line graph corresponds to the programmedheat set point. A fan setting indicator is shown between the two linearline graphs. While two linear graphs for each day are shown in FIG. 15,it is contemplated that more or less line graphs may be provided, asdesired.

In the illustrative embodiment, each linear line graph includes a numberof line segments. Each line segment corresponds to a schedule timeperiod. For example, a first segment may correspond to a “sleep” timeperiod. A second, a third and a fourth segment may correspond to a“wake”, a “leave”, and a “return” time period, respectively. As notedabove, it should be recognized that other schedule time periods may beused, if desired. If the start time of a particular schedule time periodis changed, the length and position of the corresponding line segment(s)may also change to correspond to the changed start time.

As shown in FIG. 15, each line segment may be displayed in a manner thatprovides an indication of the value of a corresponding scheduleparameter. In FIG. 15, the darker the line, the cooler the set pointtemperature. Alternatively, or in addition, color or any other suitablevisually discernable indicator may be used, as desired, to provide anindication of the value of a corresponding schedule parameter. In someembodiments, a scale (not shown) may be provided that associates asegment display characteristic to a schedule parameter value. Forexample, a color scale may be provided that associates a particularcolor to a set point particular temperature. By using the color scale,the user may be able to determine the value of the schedule parameterfrom simply viewing the display characteristics of the line segmentsshown in FIG. 15. It is believed that this embodiment may also providean intuitive interface that may help a user get a more complete pictureof the schedule without having to traverse many different displayscreens.

Having thus described the several embodiments of the present invention,those of skill in the art will readily appreciate that other embodimentsmay be made and used which fall within the scope of the claims attachedhereto. Numerous advantages of the invention covered by this documenthave been set forth in the foregoing description. It will be understoodthat this disclosure is, in many respects, only illustrative. Changescan be made with respect to various elements described herein withoutexceeding the scope of the invention.

1-81. (canceled)
 82. A thermostat comprising: a touch screen; and acontroller adapted to display a display image on the touch screen, thedisplay image having a portion that coincides with a touch region,wherein when the touch region is touched, at least part of the portionof the display image that coincides with the touch region changes from afirst display image to a second display image to indicate a firstsetting change of the thermostat.
 83. The thermostat of claim 82 whereinthe first display image includes a first setting indicator and thesecond display image includes a second setting indicator.
 84. Thethermostat of claim 82 wherein the display image displays a boundarythat traverses around at least part of the touch region.
 85. Thethermostat of claim 84 wherein the boundary traverses around all orsubstantially all of the touch region.
 86. The thermostat of claim 82wherein at least part of the portion of the display image that coincideswith the touch region changes from the second display image to the firstdisplay image when the touch region is touched a predetermined number oftimes.
 87. The thermostat of claim 82 wherein at least part of theportion of the display image that coincides with the touch regionchanges from the second display image to a third display image when thetouch region is again touched to indicate a second setting change of thethermostat.
 88. The thermostat of claim 87 wherein at least part of theportion of the display image that coincides with the touch regionchanges from the third display image to the first display image when thetouch region is again touched.
 89. The thermostat of claim 87 wherein atleast part of the portion of the display image that coincides with thetouch region changes from the third display image to a fourth displayimage when the touch region is again touched to indicate a third settingchange of the thermostat.
 90. The thermostat of claim 89 wherein atleast part of the portion of the display image that coincides with thetouch region changes from the fourth display image to the first displayimage when the touch region is again touched.
 91. The thermostat ofclaim 83 wherein the first setting indicator corresponds to a heat modeof the thermostat, and the second setting indicator corresponds to acool mode of the thermostat.
 92. The thermostat of claim 83 wherein thefirst setting indicator corresponds to a fan on mode of the thermostat,and the second setting indicator corresponds to a fan auto mode of thethermostat.
 93. A method for changing a setting of a thermostat that hasa touch screen, the method comprising: displaying a display image on thetouch screen; monitoring a touch region for a touch by a user; andchanging at least part of a portion of the display image that coincideswith the touch region to indicate a first setting change of thethermostat when the monitoring step detects that the touch region hasbeen touched by the user.
 94. The method of claim 93 further comprisingthe step of: changing at least part of the portion of the display imagethat coincides with the touch region to indicate a second setting changeof the thermostat when the monitoring step detects that the touch regionhas again been touched by the user.
 95. A method for changing a settingof a thermostat between a number of setting options including a firstsetting option and a last setting option, the thermostat having a touchscreen, the method comprising: displaying a display image on the touchscreen; monitoring a touch region on the touch screen for a touch by auser, a portion of the display image coinciding with the touch region;and changing at least part of the portion of the display image thatcoincides with the touch region to indicate the setting has been changedto a next setting option each time the monitoring step detects that thetouch region has been touched by the user.
 96. The method of claim 95further comprising: changing at least part of the portion of the displayimage to indicate the setting has been changed to the last settingoption when the monitoring step detects that the touch region has beentouched by the user a sufficient number of times to reach the lastsetting option.
 97. The method of claim 96 further comprising: changingat least part of the portion of the display image to indicate thesetting has been changed to the first setting option when the monitoringstep detects that the touch region has been touched a next time.
 98. Themethod of claim 97 wherein the setting options correspond to thermostatsystem modes.
 99. The method of claim 97 wherein the setting optionscorrespond to thermostat fan modes.
 100. A method for selecting asetting of a thermostat from a number of setting options including afirst setting option and a last setting option, the thermostat having atouch screen, the method comprising: displaying a first settingindicator on the touch screen, the first setting indicator correspondingto the first setting option; monitoring a touch region for a touch by auser; and removing the first setting indicator and displaying a secondsetting indicator when the monitoring step detects that the touch regionhas been touched by the user, the second setting indicator correspondingto a second setting option of the thermostat.
 101. The method of claim100 further comprising removing the second setting indicator anddisplaying the first setting indicator when the monitoring step detectsthat the touch region has again been touched by the user.
 102. Themethod of claim 100 further comprising: removing the second settingindicator and displaying a third setting indicator when the monitoringstep detects that the touch region has again been touched by the user,the third setting indicator corresponding to a third setting option.103. The method of claim 102 further comprising removing the thirdsetting indicator and displaying the first setting indicator when themonitoring step detects that the touch region has again been touched bythe user.
 104. The method of claim 102 further comprising: removing thethird setting indicator and displaying a fourth setting indicator whenthe monitoring step detects that the touch region has again been touchedby the user, the fourth setting indicator corresponding to a fourthsetting option.
 105. The method of claim 104 further comprising removingthe fourth setting indicator and displaying the first setting indicatorwhen the monitoring step detects that the touch region has again beentouched by the user.
 106. The method of claim 100 further comprising:removing a next to last setting indicator and displaying the lastsetting indicator when the monitoring step detects that the touch regionhas been touched a sufficient number of times to reach the last settingindicator.
 107. The method of claim 106 further comprising: removing thelast setting indicator and displaying the first setting indicator whenthe monitoring step detects that the touch region has again been touchedby the user.
 108. A thermostat comprising: a touch screen; a controlleradapted to display a display image on the touch screen, the displayimage having a portion that coincides with a touch region, wherein whenthe touch region is touched, at least part of the portion of the displayimage that coincides with the touch region changes from a first displayimage to a second display image to indicate a first setting change ofthe thermostat; and the display image displays a boundary that traversesaround at least part of the touch region, wherein the boundary isgenerally rectangular in shape.
 109. The thermostat of claim 108 whereinthe boundary is generally rectangular in shape.
 110. The thermostat ofclaim 109 wherein the generally rectangular shaped boundary includesrounded off corners.
 111. The thermostat of claim 110 wherein thegenerally rectangular shaped boundary includes one or more gaps in theboundary.
 112. The thermostat of claim 110 wherein the generallyrectangular shaped boundary includes a first region and a second region,wherein a line is displayed between the first region and the secondregion.
 113. The thermostat of claim 112 wherein the first display imageincludes a first setting indicator and the second display image includesa second setting indicator, wherein the first setting indicator and thesecond setting indicator are displayed in the second region of thegenerally rectangular shaped boundary, and wherein the first displayimage and the second display image both display a common header in thefirst region of the generally rectangular boundary.
 114. The thermostatof claim 113 wherein the first setting indicator and the second settingindicator relate to thermostat fan mode settings, and the common headeris a fan mode heading.
 115. The thermostat of claim 113 wherein thefirst setting indicator and the second setting indicator relate tothermostat system mode settings, and the common header is a system modeheading.